What

Adds send-many-ft.clar — a generic contract for batch SIP-010 fungible token transfers. Works with any SIP-010 token, no per-token deployment needed.

Key Pattern: Trait as Fold Accumulator

The main challenge: Clarity's fold helpers have a fixed (element, accumulator) signature and can't access trait parameters from the outer scope.

Solution: Pass the <ft-trait> itself as the fold accumulator. The fold helper receives it as a parameter, calls contract-call? token transfer directly, and returns the trait for the next iteration. Counts are tracked via data-vars.

;; Trait flows through as accumulator
(fold send-ft entries token)

;; Fold helper receives trait, can call it
(define-private (send-ft (entry {...}) (token <ft-trait>))
  (match (contract-call? token transfer ...)
    success (begin (var-set ok-count (+ (var-get ok-count) u1)) token)
    error   (begin (var-set fail-count (+ (var-get fail-count) u1)) token)))

Clarity 4 Post Conditions

Uses restrict-assets? with with-ft — caller passes the token name for the post condition:

(restrict-assets? sender
  ((with-ft (contract-of token) token-name total-amount))
  ;; body
)

If actual transfers exceed total-amount, the entire tx rolls back. No client-side post conditions needed.

Interface

(send-many
  token          ;; <ft-trait> — any SIP-010 token
  token-name     ;; (string-ascii 128) — the define-fungible-token name
  l1 l2 l3       ;; three lists (5000+5000+4995 = 14,995 max)
  total-amount)  ;; uint — sum of all amounts (for post-condition)

Returns {ok: uint, fail: uint} — successful and failed transfer counts.

Features

• Generic: single deployment, works with any SIP-010 token
• 14,995 recipients per tx: same 3-list pattern as send-many.clar
• Fault-tolerant: failed transfers don't abort the batch
• In-contract post conditions: Clarity 4 restrict-assets? enforces limits
• Event emission: BatchTransfer print with full summary